Thanks for reviewing.

As expressed on your original PR this feels too big to fit in this section, and belongs in a tutorial in my opinion

I believe the reference docs should be the complete and authoritative source of information. I.e. an official tutorial should bring no more information than what you can piece together from the references.

Of all I wrote, I think only this paragraph doesn't bring novel information important to the motion_mirroring property. It is more like an usage tip:

Notice that if you want the repeatition to pixel-perfect match a [Texture2D] displayed by a child node, you should account for any scale applied to the texture when defining this interval. E.g., if you use a child [Sprite2D] scaled to [code]0.5[/code] to display a 600x600 texture, and want this sprite to be repeated continuously horizontally, you should set the mirroring to [code]Vector2(300, 0)[/code].

But even then, I don't think such an usage tip is out of place in a reference documentation: the reference should be more complete and thorough on the details than a tutorial, not less.

Sorry for the long delay. I applied all the fixes, thanks.

How can CI fail in building C++ code if I didn't touch it?

Committed @Mickeon's suggestions and squashed the commits.

Thanks! And congrats for your first merged Godot contribution 🎉

Cherry-picked for 4.2.2.
Cherry-picked for 4.1.4.